<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html xmlns:s="http://xbrl.org/specification/2007" xmlns:diff="http://xbrl.org/specification/2007/diff"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>Function Registry Process Documentation 1.0</title><link rel="stylesheet" type="text/css" href="styles.css"></head><body>
	  <div class="head">
<h1><a name="title" id="title"></a>Function Registry Process Documentation 1.0</h1>
<h2>Draft Public Working Draft 11 July 2008</h2><p>Copyright ©2008 XBRL International Inc., All Rights Reserved.</p><dl><dt>This version:</dt><dd>FunctionRegistryProcess-DPWD-2008-07-11.html</dd><dt>Editors:</dt><dd><a name="auth-hugh" id="auth-hugh"></a>
				        Hugh Wallis,
	
				         XBRL International Inc.
				         <a href="mailto:hughwallis@xbrl.org">&lt;hughwallis@xbrl.org&gt;</a>
			      </dd><dd><a name="auth-geoff" id="auth-geoff"></a>
				        Geoff Shuetrim,
	
				         Galexy Pty. Limited
				         <a href="mailto:geoff@galexy.net">&lt;geoff@galexy.net&gt;</a>
			      </dd><dt>Contributor:</dt></dl><hr><div><h2><a name="status" id="status"></a>Status</h2><p>Circulation of this  Draft Public Working Draft is restricted to participants in XBRL International and is not appropriate to cite from other sources. This document is normative. 
            Other documents may supersede this document. 
          
          Recipients are invited to submit comments to
        <a href="mailto:geoff@galexy.net">geoff@galexy.net</a>,
				
          and to submit notification of any relevant patent rights 
          of which they are aware and provide supporting 
          documentation.
        </p></div><div>
<h2><a name="abstract" id="abstract"></a>Abstract</h2>
			      <p>
				This document describes the XBRL International process by which a registry for XBRL functions is 
				updated. The function registry is an online listing of XBRL functions, along with structured information
				 about their purpose, usage, and their associated conformance tests.
			</p>
		    </div></div>
	
	  <div class="toc">
<h2><a name="contents" id="contents"></a>Table of Contents</h2><p class="toc">1 <a href="#sec-goals">Goals</a><br>
   1.1 <a href="#sec-intended-audience">Intended audience</a><br>
   1.2 <a href="#sec-doc-scope">Document scope</a><br>
   1.3 <a href="#sec-org-of-doc">Organisation of this document</a><br>
   1.4 <a href="#sec-terminology">Terminology and document conventions</a><br>
   1.5 <a href="#sec-lang-indepence">Language independence</a><br>
2 <a href="#sec-update-proc">Update process</a><br>
3 <a href="#sec-criteria">Criteria</a><br>
4 <a href="#sec-norm-stat-func-in-FR">Normative status of functions in the FR</a><br>
</p>
<h3><a name="appendices" id="appendices"></a>Appendices</h3><p class="toc">A <a href="#sec-references-nn">References (non-normative)</a><br>
B <a href="#sec-ip-status">Intellectual property status (non-normative)</a><br>
C <a href="#sec-acknowledgements-nn">Acknowledgements (non-normative)</a><br>
D <a href="#sec-doc-history-nn"> Document history (non-normative)</a><br>
</p><h3><a name="figures" id="figures"></a>Figure</h3><p class="toc">1 <a href="#fig-Approval process for FR entries">Approval process for FR entries</a><br></p>
<h3><a name="definitions" id="definitions"></a>Definitions</h3><p class="toc"><a href="#term-cr">CR</a><br><a href="#term-dcr">DCR</a><br><a href="#term-fr">FR</a><br><a href="#term-frag">FRAG</a><br><a href="#term-fwg">FWG</a><br><a href="#term-isc">ISC</a><br><a href="#term-iwd">IWD</a><br><a href="#term-pwd">PWD</a><br><a href="#term-xbrl">XBRL</a><br><a href="#term-xsb">XSB</a><br><a href="#term-rfc2119">rfc2119 terminology</a><br></p></div><hr><div class="body">
	
		    <div class="div1"><a name="sec-goals" id="sec-goals"></a>
			      <h1>1 Goals</h1>
			      <p>
				The goal of the Function Registry (FR) is to be a public, online data set that documents functions
				 intended to operate on information expressed using XBRL.  Additions and other changes to the FR, like
				  other XBRL International work products, will proceed through a series of steps whose goal is to 
				  maximise the utility of the functions included in the registry.
			</p>
				
			      <div class="div2"><a name="sec-intended-audience" id="sec-intended-audience"></a>
				        <h2>1.1 Intended audience</h2>
				        <p>
					This document is intended for those with an interest in contributing new functions to the FR.
				</p>
			      </div>

			      <div class="div2"><a name="sec-doc-scope" id="sec-doc-scope"></a>
				        <h2>1.2 Document scope</h2>
				        <p>
					The scope of this document encompasses the processes by which changes are made to the FR.
				</p>
			      </div>

			      <div class="div2"><a name="sec-org-of-doc" id="sec-org-of-doc"></a>
				        <h2>1.3 Organisation of this document</h2>
				        <p>
					This document consists of the following sections in addition to this introduction:
				</p>
				        <ul>
					          <li> Process model for changes to the FR; </li>
					          <li> Normative status of functions included in the online resource and its effect on software.</li>
				        </ul>
			      </div>

			      <div class="div2"><a name="sec-terminology" id="sec-terminology"></a>
				        <h2>1.4 Terminology and document conventions</h2>
				        <p>
				Terminology used in XBRL frequently overlaps with terminology from other fields.
				</p>
			         <p><span class="definition"><a name="term-rfc2119" id="term-rfc2119" title="rfc2119 terminology"></a>
    The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, 
    SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL, in this
    specification, are to be interpreted as described in 
    <a href="#RFC2119">[IETF RFC 2119]</a>.
  </span></p>
				
				        <p><span class="definition"><a name="term-cr" id="term-cr" title="CR"></a><span class="term">CR</span> refers to a Candidate Recommendation
 				</span></p>
 				       <p><span class="definition"><a name="term-dcr" id="term-dcr" title="DCR"></a><span class="term">DCR</span> refers to a Draft Candidate Recommendation
 				</span></p>
 				       <p><span class="definition"><a name="term-fr" id="term-fr" title="FR"></a><span class="term">FR</span> refers to a Function Registry
 				</span></p>
 				       <p><span class="definition"><a name="term-frag" id="term-frag" title="FRAG"></a><span class="term">FRAG</span> refers to a Function Approval Group
 				</span></p>
 				       <p><span class="definition"><a name="term-isc" id="term-isc" title="ISC"></a><span class="term">ISC</span> refers to a International Steering Committee
 				</span></p>
 				       <p><span class="definition"><a name="term-fwg" id="term-fwg" title="FWG"></a><span class="term">FWG</span> refers to a Formula Working Group
 				</span></p>
 				       <p><span class="definition"><a name="term-iwd" id="term-iwd" title="IWD"></a><span class="term">IWD</span> refers to a Internal Working Draft
 				</span></p>
 				       <p><span class="definition"><a name="term-pwd" id="term-pwd" title="PWD"></a><span class="term">PWD</span> refers to a Public Working Draft
 				</span></p>
 				       <p><span class="definition"><a name="term-xbrl" id="term-xbrl" title="XBRL"></a><span class="term">XBRL</span> refers to a XBRL 2.1 recommendation [XBRL]
 				</span></p>
 				       <p><span class="definition"><a name="term-xsb" id="term-xsb" title="XSB"></a><span class="term">XSB</span> refers to XBRL International Standards Board
 				</span></p>			
				        <p>
					Italics are used for rhetorical emphasis only and do not convey any special normative meaning.
				</p>
				     </div>
				
				     <div class="div2"><a name="sec-lang-indepence" id="sec-lang-indepence"></a>
					       <h2>1.5 Language independence</h2>
						      <p>
							All documentation supporting a function MUST be provided in English, and MAY be provided in 
							additional languages.  The official language of XBRL International is UK English.
						</p>
				     </div>
			   </div>
				
		    <div class="div1"><a name="sec-update-proc" id="sec-update-proc"></a>
			      <h1>2 Update process</h1>
				     <p>
					The process by which a function is added to the FR is depicted in Figure 1 below. This is modelled on the standard processes by which XBRL International Working Group work product becomes a RECOMMENDATION.  The steps that a successful entry in the FR will proceed through as set out below:
				</p>
				     <ol>
					       <li>
						The submitter of a new function creates an IWD containing all of the information needed and 
						requests the Function Registry Approval Group (FRAG) to enter it into the FR.
					</li>
					       <li>
						The FRAG MAY suggest modifications to the proposal and request the submitters to resubmit 
						the proposal after making those modifications. In the event that there is more than one 
						submission made for similar requirements the FRAG may request the submitters to agree a 
						common solution between themselves and resubmit a single joint IWD. If this is not 
						acceptable to the submitters the ISC will be requested to arbitrate.
					</li>
					       <li>
						The FRAG approves the requirements.  They then conduct a technical evaluation of the 
						proposal. If they determine that wider technical evaluation is necessary they then submit the 
						IWD to the FWG for additional technical evaluation.
					</li>
					       <li>
						If requested in step 3 the FWG deliberates the IWD.
					</li>
					       <li>
						If requested in step 3 the FWG recommends to the FRAG that they approve release of the IWD as a PWD.
					</li>
					       <li>
						The FRAG approves the IWD and recommends to the XSB that it be released as a PWD.
					</li>
					       <li>
						The XSB approves publication as a PWD
					</li>
					       <li>
						The FRAG calls for two implementations of the function if they do not already exist.
					</li>
					       <li>
						The FRAG enters the new function into the FR with its status set to PWD.  A notice of its 
						addition is made to the XBRL-INT and XBRL-Public mailing lists and feedback is requested.
					</li>
					       <li>
						A minimum of forty-five days of public review follow.
					</li>
					       <li>
						The FRAG or, if it decides to delegate this step, the FWG verifies that the conformance suite 
						tests are valid and that there are two separate implementations that pass them.
					</li>
					       <li>
						The FRAG or, if it decides to delegate this step, the FWG makes any necessary amendments 
						pursuant to the PWD feedback and, unless it determines that a new PWD is necessary, the 
						FRAG recommends to the XSB that a DCR be published (amended if appropriate) as a CR.
					</li>
					       <li>
						The XSB approves the CR.
					</li>
					       <li>
						Two weeks pass during which only minor editorial changes MAY be made.  Such changes MUST 
						be approved by the FRAG.  Substantive changes require a new DCR (return to step 12).  The 
						FRAG recommends to the XSB that it be published as a recommendation who in turn 
						recommend such to the ISC.
					</li>
					       <li>
						The ISC approves the recommendation.
					</li>
					       <p>
					The process by which an function may be updated in the FR is analogous.   If errata are discovered in 
					any function then a new version of the function will be entered into the FR following the same process 
					as that used for errata corrections to the specification itself. The effective date of the errata corrected 
					version will be later than that of the original and will thus supersede it.  Superseded functions will be 
					identified as deprecated in the FR.
					</p>
				     </ol>
		    </div>
		    <div class="div1"><a name="sec-criteria" id="sec-criteria"></a>
				     <h1>3 Criteria</h1>
					    <p>
						A function must meet these criteria to be approved by the FRAG:
					</p>
					    <ul>
						      <li> Semantically distinct from existing functions; </li>
						      <li> Of sufficient generality to be of broad use; </li>
						      <li> Sufficiently well documented to encourage correct usage.</li>
					    </ul>
			   </div>
			   <div class="div1"><a name="sec-norm-stat-func-in-FR" id="sec-norm-stat-func-in-FR"></a>
				     <h1>4 Normative status of functions in the FR</h1>
				     <p>
				Once a function has the status of REC in the FR it shall have the same normative status as any specification recommended by XBRL International.
				</p>
				     <p>
				It is expected that software vendors will make claims regarding which additional functions they support. They must point to successful exercising of the relevant conformance suite tests in order to substantiate such claims.
				</p>
			   </div>
			   <div class="chunkHeading"><a name="fig-Approval process for FR entries" id="fig-Approval process for FR entries"></a>Figure 1: Approval process for FR entries</div><div class="figure">
					    
					    <img src="Figure_2-FR_Entries.gif">
			   </div>
	  </div>
	
	  <div class="back">
      <div class="div1"><a name="sec-references-nn" id="sec-references-nn"></a>

         <h1>Appendix A References (non-normative)</h1>
    	    <dl>
		  	       <p>
		  		The hyperlinks to HTML format XBRL International documents are to the non-normative versions of those documents but are provided in this format for convenience. Those documents indicate the location of their relevant normative versions.
		  	</p>
	  		       
	  		       
	  	        
       	<dt class="label"><a name="RFC2119" id="RFC2119"></a>IETF RFC 2119</dt><dd>IETF (Internet Engineering Task Force). "RFC 2119: Key words for use in RFCs to  Indicate Requirement Levels"<br>Scott Bradner.<br>(See <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>)</dd><dt class="label"><a name="ISO" id="ISO"></a>ISO<span class="error">This reference is not cited.</span></dt><dd>International Standards Organisation. "
		ISO 4217 Currency codes, ISO 639 Language codes, ISO 3166
		Country codes, ISO 8601 international standard numeric date and
		time representations.
	"<br>(See <a href="http://www.iso.ch/">http://www.iso.ch/</a>)</dd><dt class="label"><a name="XBRL" id="XBRL"></a>XBRL 2.1<span class="error">This reference is not cited.</span></dt><dd>XBRL International Inc.. "Extensible Business Reporting Language (XBRL) 2.1 Includes Corrected Errata Up To 2008-07-02"<br>Phillip Engel, Walter Hamscher, Geoff Shuetrim, David vun Kannon, and Hugh Wallis.<br>(See <a href="http://www.xbrl.org/Specification/XBRL-RECOMMENDATION-2003-12-31+Corrected-Errata-2008-07-02.htm">http://www.xbrl.org/Specification/XBRL-RECOMMENDATION-2003-12-31+Corrected-Errata-2008-07-02.htm</a>)</dd></dl>
	     </div>
	
	     <div class="div1"><a name="sec-ip-status" id="sec-ip-status"></a>
        <h1>Appendix B Intellectual property status (non-normative)</h1>
        
        <p>
          This document and translations of it may be copied and
          furnished to others, and derivative works that comment on or
          otherwise explain it or assist in its implementation may be
          prepared, copied, published and distributed, in whole or in
          part, without restriction of any kind, provided that the above
          copyright notice and this paragraph are included on all such
          copies and derivative works. However, this document itself may
          not be modified in any way, such as by removing the copyright
          notice or references to XBRL International or XBRL
          organizations, except as required to translate it into
          languages other than English. Members of XBRL International
          agree to grant certain licenses under the XBRL International
          Intellectual Property Policy 
          (<a href="http://www.xbrl.org/legal">www.xbrl.org/legal</a>).
        </p>
        <p>
          This document and the information contained herein is provided
          on an "AS IS" basis and XBRL INTERNATIONAL DISCLAIMS ALL
          WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
          ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
          INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
          MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
        </p>
        <p>
          The attention of users of this document is directed to the
          possibility that compliance with or adoption of XBRL
          International specifications may require use of an invention
          covered by patent rights. XBRL International shall not be
          responsible for identifying patents for which a license may be
          required by any XBRL International specification, or for
          conducting legal inquiries into the legal validity or scope of
          those patents that are brought to its attention. XBRL
          International specifications are prospective and advisory
          only. Prospective users are responsible for protecting
          themselves against liability for infringement of patents. XBRL
          International takes no position regarding the validity or
          scope of any intellectual property or other rights that might
          be claimed to pertain to the implementation or use of the
          technology described in this document or the extent to which
          any license under such rights might or might not be available;
          neither does it represent that it has made any effort to
          identify any such rights. Members of XBRL International agree
          to grant certain licenses under the XBRL International
          Intellectual Property Policy 
          (<a href="http://www.xbrl.org/legal">www.xbrl.org/legal</a>).
        </p>
     </div>
              
     <div class="div1"><a name="sec-acknowledgements-nn" id="sec-acknowledgements-nn"></a>
     	   <h1>Appendix C Acknowledgements (non-normative)</h1>
      		<p>
     			The participants in the XBRL Formula Working Group and public commentators have all played a role.
      		</p>
      </div>
      <div class="div1"><a name="sec-doc-history-nn" id="sec-doc-history-nn"></a>
         <h1>Appendix D  Document history (non-normative)</h1>
         <table cellpadding="5%">
					       <thead>
						         <tr>
							           <th>
								Date
							</th>
							           <th>
								Editor
							</th>
							           <th>
								Summary
							</th>
						         </tr>
					       </thead>
					       <tbody>
						         <tr>
							           <td>
								2007-07-25
							</td>
							           <td>
									Geoff Shuetrim
          					</td>	
          					   <td>
          						First draft of document prepared.
							</td>
          				</tr> 
          				<tr>
							           <td>
								2007-08-01
							</td>
							           <td>
									Geoff Shuetrim
          					</td>
          					   <td>	
          						Comments from Roland Hommes and Hugh Wallis incorporated into the document.
							</td>
          				</tr> 
          				<tr>
							           <td>
								2007-08-03
							</td>
							           <td>
									Geoff Shuetrim
          					</td>	
          					   <td>
          						Changed the choice of acronym.  Eliminated remaining reference to LRR.
							</td>
          				</tr>  
          				<tr>
							           <td>
								2007-08-03
							</td>
							           <td>
									Hugh Wallis
          					</td>	
          					   <td>
          						Corrected some spelling mistakes, headers and footers, copyright notices and updated flow chart
							</td>
          				</tr>       	     				
          			</tbody>
          		</table>
          </div>
      
	  </div>
</body></html>